Synchronizing authentication sessions between applications

ABSTRACT

Disclosed are various embodiments for synchronizing authentication sessions between applications. In one embodiment, a first authentication token is received from a first application in response to determining that the first application is authenticated with a service provider. A second authentication token is requested from a token exchange service associated with the service provider. The second authentication token is requested using the first authentication token. The second application is configured to use the second authentication token in order to access a resource of the service provider.

BACKGROUND

When a user signs onto an account with a network site using a browser, a session is created. Typically, the user provides a username and a password to the network site, though other security credentials may be provided. Upon verification of the provided security credentials and creation of the session, one or more authentication tokens may be provided to the web browser to maintain the session state. Upon subsequent requests from the network site, the browser is configured to provide the authentication tokens via a cookie, form variables, or another approach. The authentication tokens may be valid until the user explicitly ends the session by logging out or until the expiration of a predefined period of time (e.g., 30 minutes, an hour, a day, or another time period).

In contrast to browser-based sessions, mobile applications and other dedicated applications may employ a registration approach. With a registration approach, after a user provides the username and password or other credentials, the application becomes registered with a network service. As with browser sessions, an authentication token may be created and supplied to the application by the network service. The application then is configured to automatically provide the authentication token in service calls to that service. Though the user may choose to explicitly deregister the application, registration otherwise may persist indefinitely.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 is a drawing illustrating an example scenario involving synchronized authentication sessions according to an embodiment of the present disclosure.

FIG. 2 is a drawing of a networked environment according to various embodiments of the present disclosure.

FIGS. 3A-3C are flowcharts illustrating examples of functionality implemented as portions of an authentication management library executed in a client computing device in the networked environment of FIG. 2 according to various embodiments of the present disclosure.

FIG. 4 is a flowchart illustrating one example of functionality implemented as portions of a token exchange service executed in a computing environment in the networked environment of FIG. 2 according to various embodiments of the present disclosure.

FIG. 5 is a schematic block diagram that provides one example illustration of a computing environment employed in the networked environment of FIG. 2 according to various embodiments of the present disclosure.

FIG. 6 is a schematic block diagram that provides one example illustration of a client computing device employed in the networked environment of FIG. 2 according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to synchronizing authentication sessions between applications. Applications, such as mobile applications, can be classified as native applications, browser-based applications, or hybrid applications that blend the two. Native applications are dedicated applications that typically use a registration approach to authenticate with a network service. Browser-based applications employ a web-based interface for interacting with a network site. To this end, browser-based applications may include a container for launching a private instance of a browser to render the web-based interface. Browser-based applications typically use a short-lived session approach to authenticate with network sites. Hybrid applications may include native application code alongside a private browser for a web-based interface portion. The native portion may employ a registration approach, while the browser portion may employ a short-lived session approach.

Because hybrid applications may employ multiple authentication approaches, hybrid applications may require multiple sign-ons from users, even for network sites and services associated with a single user account. For example, a user may launch a hybrid application that requires the user to provide a username and password to register the application and access some functionality. However, when the user seeks to access other functionality that is browser-based, the user may be prompted to provide the username and password again to create a browser session with the network site, notwithstanding the earlier registration that may remain valid.

Various embodiments of the present disclosure facilitate a single-sign-on and a single-sign-out experience for applications using different approaches to authentication in a computing device. With the example of a hybrid application, a sign-on in the native portion may be used to bootstrap authentication in the browser portion via a token exchange approach. Similarly, a sign-on in the browser portion may be used to bootstrap authentication in the native portion via the token exchange approach. The authentication sessions may be synchronized on the client side such that expiration or log-out via one of the sessions causes the other session to expire.

With reference to FIG. 1, shown is an example scenario 100 involving synchronized authentication sessions according to an embodiment of the present disclosure. In the example scenario 100, a client computing device 103 first renders a user interface 106 a generated by a native portion of a hybrid application named “Buzzy Funnies.” The user interface 106 a includes a sign-in portion that allows the user to enter various security credentials in order to “register” the application with a network service. In particular, the user interface 106 a requests a username and a password from the user. In this example, the user has provided the username of “joe1234” and a password. The user can then select a sign-in button or another component in order to transmit the security credentials to an authentication service. The authentication service authenticates the client computing device 103 and returns an authentication token. The “Buzzy Funnies” application is subsequently configured to present the authentication token to the network service in order to access secured resources or perform secured operations.

Because the “Buzzy Funnies” application is a hybrid application, “Buzzy Funnies” includes a portion that corresponds to a web application. For example, some functionality or content in the “Buzzy Funnies” application corresponds to network page content rendered in a browser. The example scenario 100 includes a subsequent user interface 106 b that has a browser-rendered portion 109 that shows some web content. According to an embodiment of the present disclosure, rather than seeing another sign-in screen in the browser-rendered portion 109, the authenticated user is greeted with “Welcome, Joe!” In this example, the user corresponding to “joe1234” is already authenticated within the browser via an exchanged authentication token as will be described. Although the example of a hybrid application has been discussed, it is understood the principles of the present disclosure may be applied to multiple distinct applications in a computing device to facilitate a single-sign-on experience among the applications. In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.

Turning now to FIG. 2, shown is a networked environment 200 according to various embodiments. The networked environment 200 includes a computing environment 203 in data communication with one or more client computing devices 103 via a network 209. The network 209 includes, for example, the Internet, intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, or other suitable networks, etc., or any combination of two or more such networks.

The computing environment 203 may comprise, for example, a server computer or any other system providing computing capability. Alternatively, the computing environment 203 may employ a plurality of computing devices that are arranged, for example, in one or more server banks or computer banks or other arrangements. Such computing devices may be located in a single installation or may be distributed among many different geographical locations. For example, the computing environment 203 may include a plurality of computing devices that together may comprise a hosted computing resource, a grid computing resource, and/or any other distributed computing arrangement. In some cases, the computing environment 203 may correspond to an elastic computing resource where the allotted capacity of processing, network, storage, or other computing-related resources may vary over time.

Various applications and/or other functionality may be executed in the computing environment 203 according to various embodiments. Also, various data is stored in a data store 212 that is accessible to the computing environment 203. The data store 212 may be representative of a plurality of data stores 212 as can be appreciated. The data stored in the data store 212, for example, is associated with the operation of the various applications and/or functional entities described below.

The components executed on the computing environment 203, for example, includes an authentication service 215, a token exchange service 218, a token validation service 221, a network page server 224, a network service 227, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein. The authentication service 215 is executed to authenticate users in response to authentication requests. For example, a user may submit security credentials via a registration screen in a mobile application or via a sign-on network page. The authentication service 215 determines whether the security credentials validly correspond to a user account. If the security credentials are valid, the authentication service 215 issues an authentication token 230 that may be employed to access secured resources and/or perform secured operations relative to services provided by a service provider. The authentication token 230 may include information on who generated the token, an encrypted customer identifier, a level of permissions, and/or other data.

The token exchange service 218 is executed to exchange one type of authentication token 230 for another type of authentication token 230. For example, one type of authentication token 230 may pertain to browser-based sessions, while another type of authentication token 230 may pertain to registration sessions. An authentication token 230 used in a browser-based session may have a relatively short lifetime (e.g., 30 minutes, an hour, a day, etc.), while an authentication token 230 used in a registration session may have an indefinite lifetime (e.g., until explicitly revoked by the user or the service provider). In addition, the capabilities or levels of permissions associated with the different types of authentication tokens 230 may differ. As a non-limiting example, an authentication token 230 b associated with a web application 245 might grant permissions to perform only certain operations associated with the user account, which might exclude changing an account password. By contrast, an authentication token 230 a associated with a native application 242 may be able to perform all operations, including changing an account password. The different types of authentication tokens 230 may employ different formats and encompass different data in various embodiments.

The token validation service 221 may be executed to determine whether a particular authentication token 230 is valid. For example, the token validation service 221 may perform decryption, signature verification, and/or other operations to ensure that the authentication token 230 is valid. Further, where an authentication token 230 has an expiration time or can be revoked, the token validation service 221 may perform a verification that the authentication token 230 has not yet expired or has not yet been revoked.

The network page server 224 is executed to serve network pages, such as web pages and/or other forms of network content, to client computing devices 103 via the network 209. The network page server 224 may include a commercially available hypertext transfer protocol (HTTP) server such as Apache® HTTP Server, Apache® Tomcat®, Microsoft® Internet Information Services (IIS), and so on. Some of the network pages may be publicly accessible, while others of the network pages may be secured such that authentication of a client computing device 103 is a prerequisite for access.

The network service 227 corresponds to a web service or other service that receives requests and produces responses according to a service-oriented architecture. The network service 227 may utilize HTTP, simple object access protocol (SOAP), representational state transfer (REST), remote procedure call (RPC), remote method invocation (RMI), web services description language (WSDL), and/or other protocols and approaches. For example, a network service 227 may provide content for rendering within a screen of a mobile application or other dedicated application in the client computing device 103.

The network service 227 and the network page server 224 may be operated by the same service provider or a different service provider. In either case, both the network service 227 and the network page server 224 employ a shared user identity system such that a user may log-in with the same user account via the network page server 224 or the network service 227. The authentication service 215, the token exchange service 218, and the token validation service 221 may be operated by the same service provider as the network page server 224 and/or the network service 227. Alternatively, the authentication service 215, the token exchange service 218, and the token validation service 221 may be operated by a third-party identity provider.

The data stored in the data store 212 includes, for example, user account data 233, secured resources 236, and potentially other data. The user account data 233 includes various data relating to user accounts. Such data may include security credentials (e.g., usernames, passwords, hashes of usernames and/or passwords, public keys, private keys, etc.), information relating to active or expired authentication sessions, access restrictions and/or permissions for the user account, maximum lifetime of sessions associated with the user account, and/or other account information. The secured resources 236 comprise static content, dynamic content, and/or operations that are network accessible to authenticated client computing devices 103 via the network page server 224 and/or the network service 227.

The client computing device 103 is representative of a plurality of client computing devices 103 that may be coupled to the network 209. The client computing device 103 may comprise, for example, a processor-based system such as a computer system. Such a computer system may be embodied in the form of a desktop computer, a laptop computer, personal digital assistants, cellular telephones, smartphones, set-top boxes, music players, web pads, tablet computer systems, game consoles, electronic book readers, or other devices with like capability. The client computing device 103 may include a display 239. The display 239 may comprise, for example, one or more devices such as liquid crystal display (LCD) displays, gas plasma-based flat panel displays, organic light emitting diode (OLED) displays, electrophoretic ink (E Ink) displays, LCD projectors, or other types of display devices, etc.

The client computing device 103 may be configured to execute various applications such as native applications 242, web applications 245, and hybrid applications 248. These applications may include social networking applications, email applications, mapping applications, contact manager applications, imaging applications, electronic book reader applications, music player applications, video player applications, and/or other types of applications. The native applications 242 are written in a native format for the platform of the client computing device 103 such that the native applications 242 render a native user interface (UI) 251 upon the display 239. The native applications 242 may be associated with authentication tokens 230 a that facilitate access to secured resources 236 of the network page server 224 and/or the network service 227. In one embodiment, the authentication tokens 230 a are registration tokens that may have an indefinite lifetime.

The web applications 245 are containers for web-based functionality, with a user interface 251 rendered on the display 239 by a private instance of a browser 254. Such user interfaces 251 may correspond to network pages that are customized for rendering on a mobile device or other platform specific to the client computing device 103. The containers employed for the web applications 245 may be standardized such that the primary functionality is merely to launch the private instance of the browser 254 to access a predetermined uniform resource locator (URL). A web application 245 may be associated with one or more authentication tokens 230 b that facilitate access by the browser 254 to secured resources 236 of the network page server 224 and/or the network service 227. In one embodiment, the authentication tokens 230 b may correspond to cookies stored in a cookie jar of the web application 245.

A hybrid application 248 mixes the functionality of a native application 242 with a web application 245. To this end, the native container of the hybrid application 248 may include some customized functionality, as with a native application 242. However, a hybrid application 248 also includes a web application 245 to provide at least some web-based functionality. Thus, a hybrid application 248 may be associated with registration authentication tokens 230 a for use by the native container as well as browser-session authentication tokens 230 b for use by the private instance of the browser 254.

The authentication management library 257 corresponds to the client-side code that implements synchronization of authentication sessions across applications. To this end, the authentication management library 257 may employ a standalone service in communication with various applications executed in the client computing device 103. Alternatively, or additionally, at least a portion of the authentication management library 257 may be included within or linked to various applications executed in the client computing device 103. The operation of the authentication management library 257 may be configured based at least in part on parameters stored within an authentication management configuration 260. For example, the authentication management configuration 260 may enumerate which applications are permitted or not permitted to participate in synchronized authentication sessions. Additionally, an operating system 263 may be executed in the client computing device 103.

Next, a general description of the operation of the various components of the networked environment 200 is provided. To begin, a user installs and/or configures a plurality of applications in the client computing device 103 which employ the authentication management library 257. For purposes of discussion herein, a hybrid application 248 may be considered to be a plurality of applications, namely, the native container of the hybrid application 248 and the web application 245, as both may employ different authentication tokens 230. The user establishes or has previously established an account with a service provider, thereby resulting in the creation of security credentials for the account.

At some point, the user enters the security credentials into a user interface 251 of an application. This may correspond to a registration process for a native application 242 or a hybrid application 248 or a sign-in process for a web application 245. Accordingly, the security credentials are provided to the authentication service 215, which generates and returns an authentication token 230. In some cases, the authentication token 230 is returned via the network page server 224 or the network service 227.

Subsequently, the user employs another application (or a web application 245 within a hybrid application 248) and the other application encounters a secured resource 236 for which authentication is a prerequisite. Both of these applications employ the authentication management library 257. The authentication management library 257 is configured to request a new authentication token 230 for the other application using the previous authentication token 230 of the first application. Consequently, the other application becomes authenticated and can access secured resources 236 of the network page server 224 and/or the network service 227 without having to prompt the user to enter the security credentials. The authentication management library 257 may be configured to synchronize these authentication sessions to provide a single log-out experience as well as to refresh authentication tokens 230 that expire while another authentication token 230 remains valid.

In order to facilitate sign-on detection, log-out detection, token expiration, token exchange, and/or other communication between applications, various techniques involving application signature validation and/or secure keys signed by a trusted source may be employed. On an untrusted platform, verifying the source of an application may be important to avoid communicating authentication tokens 230 to untrusted applications. Various approaches to secure communication between applications are described in U.S. Patent Application entitled “SECURE COMMUNICATION BETWEEN APPLICATIONS ON UNTRUSTED PLATFORMS,” filed Sep. 11, 2013 under Ser. No. 14/023,663, which is incorporated herein by reference in its entirety.

Referring next to FIG. 3A, shown is a flowchart that provides one example of the operation of a portion of the authentication management library 257 according to various embodiments. Specifically, the flowchart of FIG. 3A pertains to a bootstrapping procedure where a valid token for one application is used to obtain a valid token for another application, thereby implementing a single sign-on for the applications. The applications may be implemented in one or more client computing devices 103 (FIG. 2). It is understood that the flowchart of FIG. 3A provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the authentication management library 257 as described herein. As an alternative, the flowchart of FIG. 3A may be viewed as depicting an example of steps of a method implemented in at least one client computing device 103 according to one or more embodiments.

Beginning with box 303, the authentication management library 257 determines that a first application is to be authenticated for a service provider. For example, a native application 242 (FIG. 2) or a hybrid application 248 (FIG. 2) may inform the authentication management library 257 that a sign-in user interface 251 (FIG. 2) is to be presented to the user, or otherwise, that security credentials for a user account are to be requested from the user. In the case of a web application 245 (FIG. 2) (either standalone or embedded in a hybrid application 248), a predetermined sign-in uniform resource locator (URL) may be intercepted. Alternatively, a network page obtained by the web application 245 may be analyzed to determine whether it elicits security credentials from the user.

In box 306, the authentication management library 257 determines whether the first application permits a synchronized session. For example, a hook in the authentication management library 257 may be present to allow the first application to determine whether to synchronize authentication. In some cases, the first application may desire not to synchronize authentication and instead prompt the user to supply security credentials. Such cases may be employed, for example, to ensure that the authenticated user still maintains control over the client computing device 103. If the first application does not permit a synchronized session, the authentication management library 257 continues to box 307.

If, instead, the first application does permit a synchronized session, the authentication management library 257 moves from box 306 to box 309. In box 309, the authentication management library 257 determines whether a second application accessible to the authentication management library 257 is authenticated for the same user account for which the first application is to be authenticated. If a second application is not authenticated, the authentication management library 257 proceeds to box 307.

If, instead, a second application accessible to the authentication management library 257 is authenticated, the authentication management library 257 proceeds from box 309 to box 312. In box 312, the authentication management library 257 receives a first authentication token 230 (FIG. 2) from the second application. Where the second application is a web application 245, the authentication management library 257 may read the first authentication token 230 from a cookie jar associated with the web application 245. Where the second application is a native application 242 or a hybrid application 248, the authentication management library 257 may employ an application programming interface (API) call to retrieve the first authentication token 230. In some embodiments where applications are sandboxed, a special service that facilitates secure inter-process communication may be employed to retrieve and/or exchange authentication tokens 230.

In box 315, the authentication management library 257 requests a second authentication token 230 from a token exchange service 218 (FIG. 2) via a network 209 (FIG. 2). The request may specify a desired format for the second authentication token 230, where the desired format is usable by the first application. For example, where the first application is a web application 245, the desired format may be a browser-based session format with a predetermined maximum lifetime. Where the first application is a native application 242 or a hybrid application 248, the desired format may be a registration session format with an indefinite maximum lifetime.

In box 318, the authentication management library 257 determines whether the requested second authentication token 230 has been received from the token exchange service 218. For example, the request may fail due to an invalid token, lack of permissions, revoked access, and/or other reasons. If the second authentication token 230 is not received, the authentication management library 257 proceeds to box 307.

If, instead, the second authentication token 230 is received, the authentication management library 257 transitions from box 318 to box 321. In box 321, the authentication management library 257 configures the first application to use the second authentication token 230 to access resources of the network service 227 (FIG. 2) and/or the network page server 224 (FIG. 2). For example, the authentication management library 257 may store a cookie containing the second authentication token 230 in a cookie jar of a web application 245. In one embodiment, the cookie may be generated by the authentication management library 257. In another example, the authentication management library 257 may provide the second authentication token 230 to a native application 242 and/or a hybrid application 248 via an API call.

The authentication management library 257 may cause the application to proceed with accessing a secured resource 236 (FIG. 2) for which authentication is a prerequisite. In one embodiment, where a sign-on URL is intercepted, the authentication management library 257 may configure a web application 245 to proceed automatically to a destination URL of the sign-on URL, e.g., a URL that is to be accessed after the user has been authenticated. Thus, the sign-on URL may be entirely bypassed. Thereafter, the portion of the authentication management library 257 ends.

In box 307, synchronized sessions are not currently available, so the authentication management library 257 configures the first application to elicit security credentials from the user for authentication. For example, the first application may be permitted to render a sign-on user interface 251 (FIG. 2) that elicits a username, a password, and/or other security credentials from the user. Thereafter, the portion of the authentication management library 257 ends. An authentication token 230 may subsequently be received from an authentication service 215 (FIG. 2) and may be used in synchronizing sessions of other applications executed in the client computing device 103 in some cases.

Moving on to FIG. 3B, shown is a flowchart that provides one example of the operation of another portion of the authentication management library 257 according to various embodiments. In particular, the flowchart of FIG. 3B pertains to a log-out procedure whereby multiple applications are logged out via a single log-out request. The applications may be implemented in one or more client computing devices 103. It is understood that the flowchart of FIG. 3B provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the other portion of the authentication management library 257 as described herein. As an alternative, the flowchart of FIG. 3B may be viewed as depicting an example of steps of a method implemented in at least one client computing device 103 (FIG. 2) according to one or more embodiments.

Beginning with box 324, the authentication management library 257 receives a log-out indication from a user in association with a synchronized authentication session. For example, the authentication management library 257 may detect that a user has selected a log-out component in a user interface 251 (FIG. 2) rendered by a native application 242 (FIG. 2) or a hybrid application 248 (FIG. 2). In the case of a web application 245, the authentication management library 257 may intercept an access by a browser 254 (FIG. 2) of a predetermined uniform resource locator (URL) that is associated with a log-out operation.

In box 327, the authentication management library 257 determines an application that is associated with the synchronized authentication session. In box 330, the authentication management library 257 performs one or more actions to invalidate the authentication token 230 (FIG. 2) corresponding to the application. For example, the authentication management library 257 may communicate the authentication token 230 to the token validation service 221 (FIG. 2) in a request that the authentication token 230 be invalidated or revoked. The authentication management library 257 may remove the authentication token 230 from a cookie jar of the application and/or may send an invalidation indication to the application via an application programming interface (API) call. In one embodiment, the application may be configured to send a log-out request or token invalidation request to the token validation service 221 in response to receiving a message from the authentication management library 257.

In box 333, the authentication management library 257 determines whether another application is participating in the synchronized application session. If another application is participating, the authentication management library 257 returns to box 327 and determines the other application. If another application is not participating, the portion of the authentication management library 257 ends.

Continuing to FIG. 3C, shown is a flowchart that provides one example of the operation of yet another portion of the authentication management library 257 according to various embodiments. Specifically, the flowchart of FIG. 3C pertains to a token refresh procedure used to refresh tokens that are expiring. It is understood that the flowchart of FIG. 3C provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the other portion of the authentication management library 257 as described herein. As an alternative, the flowchart of FIG. 3C may be viewed as depicting an example of steps of a method implemented in at least one client computing device 103 (FIG. 2) according to one or more embodiments.

Beginning with box 336, the authentication management library 257 determines that an authentication token 230 (FIG. 2) in use by an application is expiring or has been revoked. In one example, the authentication management library 257 may detect that a web application 245 (FIG. 2) has been redirected to a sign-in uniform resource locator (URL). In another example, the authentication management library 257 may detect that a native application 242 (FIG. 2) has received an expired token error or invalid token error in response to a service call. In box 339, the authentication management library 257 determines participating applications in the client computing device 103 that have a valid authentication token 230 for the particular synchronized authentication session.

In box 342, the authentication management library 257 determines whether another application has a valid authentication token 230. If another application does not have such a valid authentication token 230, the authentication management library 257 continues to box 345. In box 345, the authentication management library 257 configures the application having the expired or revoked authentication token 230 to elicit security credentials from the user for authentication. Thereafter, the portion of the authentication management library 257 ends.

If another application does have a valid authentication token 230, the authentication management library 257 continues from box 342 to box 348. In box 348, the authentication management library 257 obtains the valid authentication token 230 from the other application. In box 351, the authentication management library 257 receives a new authentication token 230 by providing the valid authentication token 230 to the token exchange service 218 (FIG. 2). In box 354, the authentication management library 257 configures the application to use the new authentication token 230 in place of the expired or revoked authentication token 230. It is noted that, in some cases, the application may choose to elicit security credentials from the user rather than to refresh an expired or revoked authentication token 230 via an automated process. Thereafter, the portion of the authentication management library 257 ends.

Turning now to FIG. 4, shown is a flowchart that provides one example of the operation of a portion of the token exchange service 218 according to various embodiments. It is understood that the flowchart of FIG. 4 provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the token exchange service 218 as described herein. As an alternative, the flowchart of FIG. 4 may be viewed as depicting an example of steps of a method implemented in the computing environment 203 (FIG. 2) according to one or more embodiments.

Beginning with box 403, the token exchange service 218 receives a first authentication token 230 (FIG. 2) in a token exchange request from a client computing device 103 (FIG. 2) via the network 209 (FIG. 2). The token exchange request may specify a desired format for a requested authentication token 230. In one example, the provided authentication token 230 is in a registration session token format, while the requested authentication token 230 is in a browser-based session token format. In some scenarios, the token exchange request may specify a particular level of permissions to be associated with the requested authentication token 230. For example, it may be desired to request fewer permissions for an authentication token 230 associated with a web application 245 (FIG. 2) as compared to a native application 242 (FIG. 2).

In box 406, the token exchange service 218 performs a validation on the first authentication token 230. For example, the token exchange service 218 may call the token validation service 221 (FIG. 2) to validate the first authentication token 230. In various embodiments, the first authentication token 230 may be decrypted and/or a signature of the first authentication token 230 may be verified. The first authentication token 230 may be examined to ensure that it corresponds to a correct customer identifier (which may be encrypted within the token) and/or has not expired or been revoked. In embodiments where identity federation is employed, the token validation service 221 may be operated by a different organization that is trusted by the organization that issues the authentication tokens 230 vended by the token exchange service 218. In box 409, the token exchange service 218 determines whether the first authentication token 230 is valid. If the first authentication token 230 is determined not to be valid, the token exchange service 218 returns an error in box 412. Thereafter, the portion of the token exchange service 218 ends.

If, instead, the first authentication token 230 is valid, the token exchange service 218 continues from box 409 to box 415. In box 415, the token exchange service 218 generates a second authentication token 230. For example, the second authentication token 230 may be generated in a format requested in the token exchange request. In some embodiments, the token exchange service 218 may obtain the second authentication token 230 from a trusted service operated by another organization that issues the second authentication token 230. In box 418, the token exchange service 218 sends the second authentication token 230 to the client computing device 103 via the network 209 (FIG. 2). Thereafter, the portion of the token exchange service 218 ends.

With reference to FIG. 5, shown is a schematic block diagram of the computing environment 203 according to an embodiment of the present disclosure. The computing environment 203 includes one or more computing devices 500. Each computing device 500 includes at least one processor circuit, for example, having a processor 503 and a memory 506, both of which are coupled to a local interface 509. To this end, each computing device 500 may comprise, for example, at least one server computer or like device. The local interface 509 may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated.

Stored in the memory 506 are both data and several components that are executable by the processor 503. In particular, stored in the memory 506 and executable by the processor 503 are the authentication service 215, the token exchange service 218, the token validation service 221, the network page server 224, the network service 227, and potentially other applications. Also stored in the memory 506 may be a data store 212 and other data. In addition, an operating system may be stored in the memory 506 and executable by the processor 503.

With reference to FIG. 6, shown is a schematic block diagram of the client computing device 103 according to an embodiment of the present disclosure. The client computing device 103 includes at least one processor circuit, for example, having a processor 603 and a memory 606, both of which are coupled to a local interface 609. The local interface 609 may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated. A display 239 may also be coupled to the local interface 609.

Stored in the memory 606 are both data and several components that are executable by the processor 603. In particular, stored in the memory 606 and executable by the processor 603 may be the native applications 242, the web applications 245, the hybrid applications 248, the authentication management library 257, and potentially other applications. Also stored in the memory 606 may be an authentication management configuration 260 and other data. In addition, an operating system 263 may be stored in the memory 606 and executable by the processor 603.

Referring now to both FIGS. 5 and 6, it is understood that there may be other applications that are stored in the memories 506, 606 and are executable by the respective processors 503, 603 as can be appreciated. Where any component discussed herein is implemented in the form of software, any one of a number of programming languages may be employed such as, for example, C, C++, C#, Objective C, Java®, JavaScript®, Perl, PHP, Visual Basic®, Python®, Ruby, Flash®, or other programming languages.

A number of software components are stored in the memories 506, 606 and are executable by the respective processors 503, 603. In this respect, the term “executable” means a program file that is in a form that can ultimately be run by the processors 503, 603. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of the memories 506, 606 and run by the processors 503, 603, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of the memories 506, 606 and executed by the processors 503, 603, or source code that may be interpreted by another executable program to generate instructions in a random access portion of the memories 506, 606 to be executed by the processors 503, 603, etc. An executable program may be stored in any portion or component of the memories 506, 606 including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.

The memories 506, 606 are defined herein as including both volatile and nonvolatile memory and data storage components. Volatile components are those that do not retain data values upon loss of power. Nonvolatile components are those that retain data upon a loss of power. Thus, the memories 506, 606 may comprise, for example, random access memory (RAM), read-only memory (ROM), hard disk drives, solid-state drives, USB flash drives, memory cards accessed via a memory card reader, floppy disks accessed via an associated floppy disk drive, optical discs accessed via an optical disc drive, magnetic tapes accessed via an appropriate tape drive, and/or other memory components, or a combination of any two or more of these memory components. In addition, the RAM may comprise, for example, static random access memory (SRAM), dynamic random access memory (DRAM), or magnetic random access memory (MRAM) and other such devices. The ROM may comprise, for example, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other like memory device.

Also, the processors 503, 603 may each represent multiple processors 503, 603 and/or multiple processor cores and the memories 506, 606 may each represent multiple memories 506, 606 that operate in parallel processing circuits, respectively. In such a case, the local interfaces 509, 609 may be appropriate networks that facilitate communication between any two of the multiple processors 503, 603, between any processor 503, 603 and any of the memories 506, 606, or between any two of the memories 506, 606, etc. The local interfaces 509, 609 may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. The processors 503, 603 may be of electrical or of some other available construction.

Although the authentication service 215, the token exchange service 218, the token validation service 221, the network page server 224, the network service 227, the native applications 242, the web applications 245, the hybrid applications 248, the authentication management library 257, and other various systems described herein may be embodied in software or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each can be implemented as a circuit or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits (ASICs) having appropriate logic gates, field-programmable gate arrays (FPGAs), or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein.

The flowcharts of FIGS. 3A-4 show the functionality and operation of an implementation of portions of the authentication management library 257 and the token exchange service 218. If embodied in software, each block may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as a processor 503, 603 in a computer system or other system. The machine code may be converted from the source code, etc. If embodied in hardware, each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).

Although the flowcharts of FIGS. 3A-4 depict a specific order of execution, it is understood that the order of execution may differ from that which is depicted. For example, the order of execution of two or more blocks may be scrambled relative to the order shown. Also, two or more blocks shown in succession in FIGS. 3A-4 may be executed concurrently or with partial concurrence. Further, in some embodiments, one or more of the blocks shown in FIGS. 3A-4 may be skipped or omitted. In addition, any number of counters, state variables, warning semaphores, or messages might be added to the logical flow described herein, for purposes of enhanced utility, accounting, performance measurement, or providing troubleshooting aids, etc. It is understood that all such variations are within the scope of the present disclosure.

Also, any logic or application described herein, including the authentication service 215, the token exchange service 218, the token validation service 221, the network page server 224, the network service 227, the native applications 242, the web applications 245, the hybrid applications 248, and the authentication management library 257, that comprises software or code can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, for example, a processor 503, 603 in a computer system or other system. In this sense, the logic may comprise, for example, statements including instructions and declarations that can be fetched from the computer-readable medium and executed by the instruction execution system. In the context of the present disclosure, a “computer-readable medium” can be any medium that can contain, store, or maintain the logic or application described herein for use by or in connection with the instruction execution system.

The computer-readable medium can comprise any one of many physical media such as, for example, magnetic, optical, or semiconductor media. More specific examples of a suitable computer-readable medium would include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, or optical discs. Also, the computer-readable medium may be a random access memory (RAM) including, for example, static random access memory (SRAM) and dynamic random access memory (DRAM), or magnetic random access memory (MRAM). In addition, the computer-readable medium may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other type of memory device.

It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims. 

Therefore, the following is claimed:
 1. A non-transitory computer-readable medium embodying at least one code section executable in a computing device, comprising: code that launches a browser embedded in a native application, the native application being registered for a user account to access resources of a service provider using a registration authentication token; code that intercepts an access by the browser of a predetermined uniform resource locator (URL) of the service provider, the predetermined URL corresponding to a sign-on interface configured to elicit a security credential for the user account; code that requests a browser authentication token from a token exchange service operated by the service provider using the registration authentication token, the browser authentication token being requested without eliciting the security credential from a user of the computing device; code that provides the browser authentication token to the browser, wherein the code that provides the browser authentication token to the browser is configured to set a cookie for the browser, the cookie including the browser authentication token; code that configures the browser to access a destination URL of the service provider in place of the predetermined URL, wherein the browser is configured to employ the browser authentication token to access the destination URL; and wherein the code that intercepts, the code that requests, the code that provides, and the code that configures are implemented in an authentication management library loaded by the native application.
 2. The non-transitory computer-readable medium of claim 1, further comprising: code that detects a user request to log out from the service provider; and code that invalidates the browser authentication token and the registration authentication token in response to the user request.
 3. The non-transitory computer-readable medium of claim 1, wherein the registration authentication token has an indefinite maximum lifetime, and the browser authentication token has a predetermined maximum lifetime.
 4. The non-transitory computer-readable medium of claim 1, wherein the registration authentication token is configured with a first level of permissions, and the browser authentication token is configured with a second level of permissions that is less than the first level of permissions.
 5. A system, comprising: at least one computing device; a first application executable in the at least one computing device; and a second application executable in the at least one computing device, wherein one of the first or second applications comprises a native application and the other one of the first or second applications comprises a browser-based application and wherein the at least one computing device is configured to at least: determine whether the first application is authenticated with a service provider, wherein the authentication of the first application comprises determining whether a security credential of a user validly corresponds to an account of the user; receive a first authentication token from the first application in response to determining that the first application is authenticated with the service provider; request a second authentication token from a token exchange service associated with the service provider, the second authentication token being requested using the first authentication token; and configure the second application to use the second authentication token in order to access a resource of the service provider; detect a redirection to a sign-in uniform resource locator (URL) in the second application; request a third authentication token from the token exchange service, the third authentication token being requested using the first authentication token; and configure the second application to use the third authentication token in place of the second authentication token; and configure the second application to redirect to another URL in place of the sign-in URL.
 6. The system of claim 5, wherein the first application and the second application are configured to access different services of the service provider.
 7. The system of claim 5, wherein the first authentication token comprises a registration token, and the second authentication token comprises a session cookie.
 8. The system of claim 5, wherein the first authentication token has an indefinite maximum lifetime, and the second authentication token has a predetermined maximum lifetime.
 9. The system of claim 5, wherein the second application is embedded within the first application.
 10. The system of claim 5, wherein the at least one computing device is further configured to at least configure the second application to elicit the security credential from the user in response to determining that the first application is not authenticated with the service provider.
 11. The system of claim 5, wherein the at least one computing device is further configured to at least initiate a log out from the service provider in response to a user request, wherein the log out is configured to invalidate the first authentication token and the second authentication token.
 12. The system of claim 5, wherein the at least one computing device is further configured to at least initiate a log out from the service provider in the first application in response to detecting an access of a log out uniform resource locator (URL) by the second application.
 13. The system of claim 5, wherein the at least one computing device is further configured to at least: provide an indication of the redirection to the second application; and receive a response from the second application that indicates whether the redirection is to be bypassed.
 14. The system of claim 5, wherein the first authentication token is configured with a first level of permissions, and the second authentication token is configured with a second level of permissions that is less than the first level of permissions.
 15. The system of claim 5, wherein the token exchange service is operated by a first organization that is different from a second organization that operates the service provider, and the first organization is trusted by the second organization.
 16. A method, comprising: receiving, via at least one of one or more computing devices, a first authentication token from a client computing device, the first authentication token corresponding to a registration of an application of the client computing device for a user account; validating, via at least one of the one or more computing devices, the first authentication token; generating, via at least one of the one or more computing devices, a second authentication token in response to validating the first authentication token, the second authentication token corresponding to a browser-based session for the user account; and sending, via at least one of the one or more computing devices, the second authentication token to the client computing device; receiving, via at least one of the one or more computing device, the second authentication token from the client computing device; validating, via at least one of the one or more computing device, the second authentication token; generating, via at least one of the one or more computing device, a third authentication token in response to validating the second authentication token, the third authentication token corresponding to a registration of another application for the user account; sending, via at least one of the one or more computing devices, the third authentication token to the client computing device; and wherein the first authentication token is configured with an indefinite maximum lifetime, and the second authentication token is configured with a predetermined maximum lifetime.
 17. The method of claim 16, wherein the second authentication token is sent to the client computing device in a cookie.
 18. The method of claim 16, wherein the first authentication token is configured with a first level of permissions, and the second authentication token is configured with a second level of permissions that is less than the first level of permissions.
 19. The method of claim 16, wherein a browser embedded within the application is configured to employ the second authentication token.
 20. The method of claim 16, wherein the first authentication token is received from a native application executed by the first computing device.
 21. The method of claim 16, wherein validating the first authentication token further comprises determining, via at least one of the one or more computing devices, that the first authentication token has not expired and has not been revoked. 